Hiyas, I've got two NFS persistent shares that I wish wasn't that persistent... ;) Here's the deal, I had a linux machine with NFS shares, which I tried to mount on this Win7 Ultimate computer.. used the mount command from memory and I did it wrong. share stuck but doesn't work and now the linux machine is no longer on the network. As a result I have two mounted NFS shares on my computer I can not disconnect from, resulting in that every time I open "My Computer" it takes about 1 minute before anything shows up in the window, which is very frustrating. I've been trying to get rid of these shares but they are impossible (for me at least) to get rid of. C:\Windows\system32>net use New connections will not be remembered. Status Local Remote Network ------------------------------------------------------------------------------- Unavailable K: \\192.168.1.106\usr NFS Network Unavailable L: 192.168.1.106:/usr NFS Network The command completed successfully. C:\Windows\system32>net use * /delete You have these remote connections: K: \\192.168.1.106\usr L: 192.168.1.106:/usr Continuing will cancel the connections. Do you want to continue this operation? (Y/N) [N]: yes The command completed successfully. C:\Windows\system32>net use New connections will not be remembered. Status Local Remote Network ------------------------------------------------------------------------------- Unavailable K: \\192.168.1.106\usr NFS Network Unavailable L: 192.168.1.106:/usr NFS Network The command completed successfully. NET USE command doesn't work.. Been digging through the web and I found some references to a registry key at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\ where shares are listed as ##server#share and deleting those would remove the share. didn't work. But then I found some documents on technet.microsoft.com detailing information about a unmount.exe, which apparently I should have and from my understanding correct all my problems, but I don't have this even though I have installed "Client for NFS" . http://technet.microsoft.com/en-us/library/cc725746.aspx Best Practices of NFS The umount command will disconnect a hard mount — even if the server is unavailable. http://technet.microsoft.com/en-us/library/cc770449.aspx Unmounting an NFS shared resource from a drive letter To unmount an NFS shared resource from a drive letter using the command line Open a command prompt (this does not need to be an elevated command prompt). At the command prompt, type: umount [–f] {–a | Drive}[/quote] [/quote] so. how can I fix this? any ides?

Hello. You've got several things you can try yet: 1. Try mapping a different share to one of those drive letters. Windows will complain that the drive is already in use, but it may let you do it anyway. If that is successful, disconnect from the share and it should free the drive letter. 2. If you no longer need the NFS client (you DID say the Linux box no longer exists) then just uninstall it. Windows will no longer try to connect those shares. 3. You COULD try the umount command (notice there's no "n" between the "u" and the "m"). The command: umount -f -a will force an unmount of all NFS mounted shares. 4. Last, but certainly not least, if you're comfortable with mucking around in the registry you could do a search for all occurrences of 192.168.1.106 and remove them.

I had the same problem, but finally stumbled on to this solution: 1) Open Start Menu\Programs\Administrative Tools\Services for Network File System (NFS) 2) Right click "Client for NFS" and choose "Stop Service" 3) Open CMD and run: "net use n: /delete" (replace n: with your driver letter) May or may not need to goto Explorer and right-click and "Disconnect" as well.